-
Notifications
You must be signed in to change notification settings - Fork 119
[CMake] Remove unused dependency on Foundation build directory #1260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
@swift-ci test |
I thought these linker flags were necessary, so if your investigation leads you to believe we should remove them, please elaborate since I don't quite understand all the factors involved here. I skimmed the linked Swift PR but it looks like it's gone in a few different directions so I'm unclear where things stand there, currently. |
My understanding is that these flags add a dependency to the CMake target, which is in the Foundation build directory, eg Of course, this didn't break anything so it was fine so far, but my linked frontend pull enforces that the compiler looks in the passed in
Note how it gets confused between the SDK path and the module map files from the source directories that these CMake targets are transitively adding. Basically, the Windows CI was mixing and matching files from the build directories, the source directories, and the final installed SDK directory to build each new core library like Foundation or XCTest. Once my frontend pull makes sure non-Darwin platforms use only the installed SDK directory, these flags broke the Windows CI, because it is the only platform CI that uses that SDK directory very early on with the I went ahead and got rid of it for linux and other |
Good news is that previously failing command now passed on the Windows CI with my frontend pull, bad news is the CI now can't find |
@compnerd Please review when @finagolfin is ready. |
This passed the linux CI and has no effect on the mac CI, now to see if I can get it working on Windows. |
See if this helps with swiftlang/swift#79621